What

Relicense @agentage/server-memory from UNLICENSED to MIT:

• add a root LICENSE (standard MIT text)
• set "license": "MIT" in package.json

No version bump: @agentage/server-memory is not yet on npm, so the current 0.0.1 publishes as-is.

Why

Unblocks the MIT-licensed @agentage/cli, which depends on this package. A dependency published as UNLICENSED is a licensing conflict for a permissively-licensed consumer.

How publish triggers after merge

Publishing is handled by .github/workflows/publish.yml and does not fire on an ordinary merge of this PR:

• trigger: push to master touching package.json, or manual workflow_dispatch
• release gate: a push only publishes if the head commit subject matches ^Release v, ^chore: prepare release, or ^chore(release); workflow_dispatch always counts as a release
• guard: the job skips if the current version already exists on npm

So merging this alone will not publish (the chore: relicense to MIT subject is not a release commit). The orchestrator publishes via a release commit or workflow_dispatch.